Skip to content

Conversation

hughns
Copy link
Member

@hughns hughns commented Dec 18, 2024

It turns out we've been using an unsupported sentry config option for some time.

By converting to TS it should help with maintainability.

tsconfig.json Outdated
@@ -18,6 +18,7 @@
// Workaround for https://github.com/microsoft/TypeScript/issues/55132
"useDefineForClassFields": false,
"allowImportingTsExtensions": true,
"skipLibCheck": true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to be a step back in how strict we do our typing.
Are we sure we want this? Is there no way to fix the reason we add this with yarns resolutions?
Can it get a comment why we need this now?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I concur that this is a backwards step. Unfortunately it's not just the case of some resolutions.

The main culprit appears to be @codecov/vite-plugin.

I will make this draft and lift the one material change over to a simpler PR.

@hughns hughns marked this pull request as draft January 6, 2025 10:53
@toger5
Copy link
Contributor

toger5 commented Aug 4, 2025

replaced by: #3443

@toger5 toger5 closed this Aug 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants